@ginobean Thanks, this can happen if you just compile ES (cmake / make) without any previous ES binary installation (or removed the previous binary installation).

FWIW, it should be no issue if you run sudo RetroPie-Setup/retropie_packages.sh emulationstation-dev unless you have a very dated (if not end-of-life OS) like these version (or even older):

Debian Jessie LinuxMint 18 Ubuntu 16.10 Zorin 14 ElementaryOS 0.4
and/or a very dated retropie_setup.sh script [0].

These versions are tested in scriptmodules/system.sh [1], if they report an OS Version of 8 the resources folder is not copied by scriptmodules/supplementary/emulationstation[-dev].sh[2].

NB: The above retropie_packages.sh calls eventually the scriptmodule emulationstation-dev.sh (which is an wrapper around scriptmodule emulationstation.sh).

If you want to keep the sources of ES (below RetroPie-Setup/tmp/build/) then run

retropie_packages.sh emulationstation-dev sources retropie_packages.sh emulationstation-dev build retropie_packages.sh emulationstation-dev install

[0] https://retropie.org.uk/forum/post/186708
[1] https://github.com/RetroPie/RetroPie-Setup/blob/fb5a22cfb75ea977484a0631949c80a263ce39c7/scriptmodules/system.sh#L211
[2] https://github.com/RetroPie/RetroPie-Setup/blob/fb5a22cfb75ea977484a0631949c80a263ce39c7/scriptmodules/supplementary/emulationstation.sh#L192

@etheling Hi, finished the same project...
I have spent many hours trying to get the overlay and Atari ST screen to line up. Could you Please post all the config files? I say config because Im doing mine on a Raspberry Pi 3... Tanx

Way cool @etheling !! I've been thinking about doing this same exact thing. I've been perusing for Atari 2600s that are non-functioning because I can't bring myself to 'descrate' a working one. LOL. Doesn't seem like anyone held on to a non-functioning unit. (or at least I can't find one)

Son of a birch, that is a good looking cabinet!!! Love me some woodgrain, so this is glorious all around.

As mentioned in Post#1, we are now opening chapter: Curse of Configs

@Ashpool said in CP2020 - my DIY 2Player/Trackball Control Panel:

Since my last visit, the Page for the I-Pac got a major overhaul and the new Firmware 1.55 is now called "Multi-Mode" [... ...] the old "Gamepad enabled" FW139 is now called "Alternative Firmware (Mixed Mode)" [... ...] they are mentioning now:
"This is an alternative firmware version [... ...] Retropie does not work with this configuration. The standard multiMode version (above) enables one device type at a time on the host (plus mouse) and this is required for Retropie. [...]"
Sadly, that was the Firmware I've build my concepts on (and had tested on a PC, never thought Retropie couldn't cope with it).

Well, I've tried on a fresh retropie-buster-4.6-rpi4.img install with my old IPac Configuration (Joy(1/2), Buttons(1/2)1-7 + Start and Select as Gamepad and (1/2)SW8, (1/2)A and (1/2)B as keys and it was working just fine (Quicktest on some 2 player games in lr-mame2003: Both Players Gamepad Functions where fine (upon start the messages detected I-PAC2 on Port 0 and detected I-PAC2 on Port 1 flashed up and the keyboard keys where accepted fine from mame (ie. 1A (Button M in Post #9) set to TAB opened the Mame Menu). ... What I hadn't considered (as I had not assigned any "shifts" so far) was: The assignment of a switch to act as Gamepad, Keyboard or Mousebutton is a general one, so it cannot act as Gamepad (unshifted) and as a keyboard (shifted) [though I bet that would only be a Firmware-thing] :/

This would have been my intended configuration:
Seufz.jpg

As using Hat-(UDLR) and Buttons 8,11+ (WinIPAC can assign Buttonnumbers 1-28) as shifted assigns ain't going to be of any use (i believe?), I think i heed the advice from @theink in his wonderfull guide to setting up the IPAC2 as a keyboard controller and stick to keyboard only (though his argument that the I-PAC is only recognized as one controller in gamepad-mode appears (to me) to be void nowadays [at least for the Retropie Install mentioned above with an I-PAC 2 (Firmware 1.39) configured in WinIPACV2 (V1.0.8.12)])

Edit: And I haven't tried wether it is possible to assign keyboard keys as hotkeys (no hotkey-enable button set) or not... so that could have been the next boobytrap laid out for me within this battle ;>

@cyperghost thanks for the confirmation, I guess I'll have to screw around with it some more.

Here's some pics of my cocktail arcade - I am no carpenter and messed up on the corners but overall satisfied with how it turned out!

IMG_7089.jpg IMG_7105.jpg IMG_7104.jpg

@trippy86
I'm an engineer too :) I couldn't resist the urge to build it myself, but of course it helps if you're familiar with woordworks.

If I should have changed one thing, I would have routed out some of the wood from the inside of the boards, e.g. in hexagon shapes to save weight but still keep some stiffness - this arcade weighs quite a bit :)

Wiring is not that complex with a RPi, mostly consisting of signal wires and ground wires from the iPac to the buttons. The illuminated ones need a few more but that's it. Keeping wires tidy helps the overview, but there's countless videos on YouTube - check them out.

My screen size is a 16" 5:4 and I think it's a pretty good size, and since many games run 4:3 there's only black borders in vertical arcade games. Just look at getting one that's as fast as possible (less input lag/response time), maybe a modern one with a gaming mode.

awesome job! simply amazing

@Graboid Do you have the Photoshop PSD file that you wouldn't mind sharing? Thanks!

@caver01 Your link actually dropped me off at the most recent post and I scrolled back from there. While the last picture I see is definitely more scanline than the first screenshots, the second to last still shows a lot of pixel separation.

I guess I'd have to see ut in action on my own television before I can tell if it's really more enjoyable than the current setup of crt + smoothing (yes @BobHarris, I do that too now), which is why I figured I'd just try it if it ever got into a RetroPie update.